Skip to content

Conversation

@PugTsurani
Copy link

Fixed issue #27 by capturing the Java PID and using it to determine if the server is running. No checks are made to determine if the screen session is still running; it's assumed if the Java process ends, the screen session will end.

@marcuswhybrow
Copy link

Thanks for the patch @PugTsurani, I've not neglected this patch. I'm just thinking of all the eventualities, and the best solution.

@PugTsurani
Copy link
Author

That's fine. I discovered a race condition where this occasionally fails on slower servers. Still trying to isolate the problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants